Handle granular requests configuration #1234
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
First iteration for: #834, I will follow up with client implementation after this one get validation.
Allow user to configure
inlayHints
andcodeLens
requests, and disabling unwanted features.Implementation
Handle in the server a hash of feature configuration:
Question: should I disable features by default as proposed here? To my very personal opinion, this can bring confusion with supported features documentation.
Automated Tests
Tests added:
executor
to ensure default and provided configurations are well populatedManual Tests
By switching default configuration to
false
inlib/ruby_lsp/store.rb
, then restarting, no feature should be display to user.Screenshots
inlayHints with
true
/false
default configuration:codelens with
true
/false
default configuration: